How to manage logging in C#

c# .net

Updated on 24-Apr-2025

Logging in C# can be managed in various ways depending on the size, complexity, and environment of your application (e.g., console app, ASP.NET, etc.). Here's a breakdown of the most common approaches and tools:

1. Built-in Logging with `Microsoft.Extensions.Logging` (Recommended for ASP.NET Core / .NET Core)

Setup: Add the NuGet package:

dotnet add package Microsoft.Extensions.Logging

Example:

using Microsoft.Extensions.Logging;

public class MyService
{
    private readonly ILogger<MyService> _logger;

    public MyService(ILogger<MyService> logger)
    {
        _logger = logger;
    }

    public void DoSomething()
    {
        _logger.LogInformation("Doing something at {Time}", DateTime.UtcNow);
        _logger.LogWarning("This is a warning.");
        _logger.LogError("This is an error.");
    }
}

Available log levels:

LogTrace
LogDebug
LogInformation
LogWarning
LogError
LogCritical

2. `log4net` (Great for legacy ASP.NET MVC 5 or WinForms/WPF)

Setup: Add via NuGet:

Install-Package log4net

Basic Configuration (log4net.config):

<log4net>
  <appender name="FileAppender" type="log4net.Appender.FileAppender">
    <file value="log.txt" />
    <appendToFile value="true" />
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date [%thread] %-5level %logger - %message%newline" />
    </layout>
  </appender>
  <root>
    <level value="INFO" />
    <appender-ref ref="FileAppender" />
  </root>
</log4net>

Usage:

private static readonly ILog log = LogManager.GetLogger(typeof(MyClass));

public void DoWork()
{
    log.Info("Doing work...");
    log.Error("Something went wrong!");
}

3. `NLog` (Flexible and very powerful for .NET Framework and .NET Core)

Setup:

Install-Package NLog
Install-Package NLog.Web.AspNetCore  // if using in ASP.NET Core

Basic config (nlog.config):

<nlog>
  <targets>
    <target name="logfile" xsi:type="File" fileName="file.txt" />
  </targets>
  <rules>
    <logger name="*" minlevel="Info" writeTo="logfile" />
  </rules>
</nlog>

Usage:

private static readonly NLog.Logger logger = NLog.LogManager.GetCurrentClassLogger();

public void Run()
{
    logger.Info("Running...");
    logger.Error("Error occurred!");
}

4. Simple Console/File Logger for Small Apps

public static class Logger
{
    public static void Log(string message)
    {
        var logMessage = $"{DateTime.Now:yyyy-MM-dd HH:mm:ss} - {message}";
        Console.WriteLine(logMessage);
        File.AppendAllText("log.txt", logMessage + Environment.NewLine);
    }
}

Tips for Effective Logging

Use structured logging (e.g., LogInformation("User {UserId} logged in", userId);)
Avoid excessive logging in performance-critical areas.
Always log exceptions with ex.ToString() for stack trace visibility.
Use log rotation and archiving for file-based logs.
Use log viewers (like Seq or Kibana) for better analysis.

Want help setting this up for your specific project (e.g., ASP.NET MVC 5 or Core)?

interview

How to manage logging in C#

ICSM Computer

Can you answer this question?

1 Answers

1. Built-in Logging with `Microsoft.Extensions.Logging` (Recommended for ASP.NET Core / .NET Core)

2. `log4net` (Great for legacy ASP.NET MVC 5 or WinForms/WPF)

3. `NLog` (Flexible and very powerful for .NET Framework and .NET Core)

4. Simple Console/File Logger for Small Apps

Tips for Effective Logging

Liked By

interview

How to manage logging in C#

ICSM Computer

Can you answer this question?

1 Answers

1. Built-in Logging with Microsoft.Extensions.Logging (Recommended for ASP.NET Core / .NET Core)

2. log4net (Great for legacy ASP.NET MVC 5 or WinForms/WPF)

3. NLog (Flexible and very powerful for .NET Framework and .NET Core)

4. Simple Console/File Logger for Small Apps

Tips for Effective Logging

Liked By

1. Built-in Logging with `Microsoft.Extensions.Logging` (Recommended for ASP.NET Core / .NET Core)

2. `log4net` (Great for legacy ASP.NET MVC 5 or WinForms/WPF)

3. `NLog` (Flexible and very powerful for .NET Framework and .NET Core)